Hello,

I need assistance with configuring our environment for co-existence.  I am following the following steps without any luck: http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part13.html

Our Environment: 

Exchange 2007 AD Computer Name: mail.xbb.local
DNS Entry: mail.xbb.local  10.0.1.2  (only DNS entry - no additional DNS entries for autodiscover)
(all internal)
AutoDiscover URI: https://mail.xbb.local/AutoDiscover/AutoDiscover.xml
OWA: https://mail.xbb.local/OWA
OAB: https://mail.xbb.local/OAB
EWS: https://mail.xbb.local/EWS/Exchange.asmx
Active-Sync Internal: https://mail.xbb.local/Microsoft-Server-ActiveSync
Active-Sync External: https://ll.xbb.local/Microsoft-Server-ActiveSync


Exchange 2013 AD Computer Name: exchange.xbb.local
DNS Entry: exchange.xbb.local   10.0.1.3

Steps taken:

Created Certificate on Exchange 2013 server for 2013-2007 server co-existence

change AutoDiscover SCP on Exchange 2013 to https://mail.xbb.local/AutoDiscover/AutoDiscover.xml

Changed all URL's on Exchange 2013 to match 2007:

OWA: https://mail.xbb.local/OWA
OAB: https://mail.xbb.local/OAB
EWS: https://mail.xbb.local/EWS/Exchange.asmx
Active-Sync Internal: https://mail.xbb.local/Microsoft-Server-ActiveSync
Active-Sync External: https://ll.xbb.local/Microsoft-Server-ActiveSync

After changing URL's, I enabled co-existence certificate on 2007.

Created Legacy DNS entry: legacy.xbb.local   10.0.1.2

Changed URLs: 

OWA: https://legacy.xbb.local/OWA
OAB: https://legacy.xbb.local/OAB
EWS: https://legacy,xbb.local/EWS/Exchange.asmx
Active-Sync Internal: https://legacy.xbb.local/Microsoft-Server-ActiveSync

Changed MAIL DNS Entry to 10.0.1.3  (only 1 DNS entry - used for AutoDiscover and Exchange 2007 Server AD name!)

Added legacy.xbb.local as 10.0.1.2 (same IP shared as Exchange 2007 AD Computer Name - Mail)

I am running into issues with connecting to 2007 mailboxes after making this change.  

What do I need to do differently since the same mail.xbb.local is shared as the Exchange 2007 Computer name and AutoDiscover?

Any help will be appreciated.

Thank you,

Hi mjmymmert,

Thank you for your question.

 As you said that I am running into issues with connecting to 2007 mailboxes after making this change. What is error or issue you are running into?

What do I need to do differently since the same mail.xbb.local is shared as the Exchange 2007 Computer name and AutoDiscover?  

A:  when the Autodiscover is coexisted in Exchange 2007 and Exchange2013. If the mailbox is in Exchange 2013, client will connect to Exchange 2013 CAS then to Exchange 2013 Mailbox server. If the mailbox in Exchange 2007, client will still connect to Exchange 2013 CAS then proxy to Exchange 2007 CAS. We could refer to the following link:

http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Hello Jim,

Thank you very much for the reply.

How will this work in my environment though?  mail.xbb.local would be the URL's on my Exchange 2013 server, and legacy.xbb.local the URL's on my Exchange 2007 server.  

The issue I am running into - mail.xbb.local is the AD computer name of my Exchange 2007 server.  I am not able to change the DNS IP address to legacy.xbb.local without changing that mail.xbb.local - the actual Exchange 2007 server AD computer name would not have a DNS entry then, or would automatically refresh back to the way it used to be for mail.xbb.local.

Does that make sense?

Would you please be wiling to update the scenario I created above with the exact steps I need to take for our environment?  I am extremely confused on how to set this up correctly.

Thank you,

• Edited by mjmummert 3 hours 12 minutes ago

Hi ,

If that, we could keep mail.xbb.local on Exchange 2007, then change Exchange 2013 URL into webmai.xbb.local.(it is just different from mail.xbb.local)

Then when user access owa, they will type https://webmail.xbb.local/owa.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

Hello Jim,

Thank you very much for the reply.

How will this work in my environment though?  mail.xbb.local would be the URL's on my Exchange 2013 server, and legacy.xbb.local the URL's on my Exchange 2007 server.  

The issue I am running into - mail.xbb.local is the AD computer name of my Exchange 2007 server.  I am not able to change the DNS IP address to legacy.xbb.local without changing that mail.xbb.local - the actual Exchange 2007 server AD computer name would not have a DNS entry then, or would automatically refresh back to the way it used to be for mail.xbb.local.

Does that make sense?

Would you please be wiling to update the scenario I created above with the exact steps I need to take for our environment?  I am extremely confused on how to set this up correctly.

Thank you,

• Edited by mjmummert Saturday, May 30, 2015 4:14 AM

Hello Jim,

Thank you very much for the reply.

How will this work in my environment though?  mail.xbb.local would be the URL's on my Exchange 2013 server, and legacy.xbb.local the URL's on my Exchange 2007 server.  

The issue I am running into - mail.xbb.local is the AD computer name of my Exchange 2007 server.  I am not able to change the DNS IP address to legacy.xbb.local without changing that mail.xbb.local - the actual Exchange 2007 server AD computer name would not have a DNS entry then, or would automatically refresh back to the way it used to be for mail.xbb.local.

Does that make sense?

Would you please be wiling to update the scenario I created above with the exact steps I need to take for our environment?  I am extremely confused on how to set this up correctly.

Thank you,

• Edited by mjmummert Saturday, May 30, 2015 4:14 AM

Apart from the given suggestion, I would suggest you to follow Exchange server deployment assistant that covers all the required aspects in order to accomplish this job without much issues : https://technet.microsoft.com/en-us/office/dn756393.aspx

By the way, while need to migrate users mailboxes from Exchange 2007 to 2013, this automated solution (http://www.exchangemailboxmigration.com/) could also be a good approach that helps to get this job done without downtime.